-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new prefer-readonly-type rule #237
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RebeccaStevens
added
Breaking Change
This change will require a new major release.
Type: Enhancement
Enhancement of the code, not introducing new features.
labels
Jul 25, 2021
Waiting on typescript-eslint/typescript-eslint#3658 |
RebeccaStevens
added
the
Status: Blocked
Progress on this issue is currently not possible.
label
Jul 26, 2021
RebeccaStevens
force-pushed
the
next
branch
3 times, most recently
from
July 30, 2021 00:38
59c20d3
to
ecfc4fe
Compare
RebeccaStevens
force-pushed
the
new-prefer-readonly-type
branch
from
July 30, 2021 01:39
25807fc
to
f603bf2
Compare
RebeccaStevens
force-pushed
the
next
branch
2 times, most recently
from
July 31, 2021 03:24
96c362b
to
f031720
Compare
RebeccaStevens
force-pushed
the
new-prefer-readonly-type
branch
from
July 31, 2021 03:35
f603bf2
to
32b6761
Compare
RebeccaStevens
force-pushed
the
new-prefer-readonly-type
branch
from
July 31, 2021 03:51
32b6761
to
6ae1d01
Compare
RebeccaStevens
force-pushed
the
next
branch
7 times, most recently
from
July 31, 2021 08:06
32b31f4
to
5098242
Compare
RebeccaStevens
force-pushed
the
new-prefer-readonly-type
branch
from
July 31, 2021 08:08
6ae1d01
to
2efa1b3
Compare
RebeccaStevens
force-pushed
the
new-prefer-readonly-type
branch
from
July 31, 2021 08:10
2efa1b3
to
1bddef2
Compare
BREAKING CHANGE: Node 12.4.0 or new is now required
BREAKING CHANGE: removed stylitic ruleset in favor of stylistic ruleset
Remove dev-dependencies that aren't needed for testing and aren't compatable with all node versions being tested against.
BREAKING CHANGE: rule "prefer-type-literal" has been removed.
…ual tsconfig file
removed: - @typescript-eslint/explicit-function-return-type added: - @typescript-eslint/prefer-readonly - @typescript-eslint/prefer-readonly-parameter-types - @typescript-eslint/switch-exhaustiveness-check - @typescript-eslint/prefer-const BREAKING CHANGE: update recommended external rules
…y default BREAKING CHANGE: allowMutableReturnType is now on by default re #153
RebeccaStevens
force-pushed
the
new-prefer-readonly-type
branch
from
July 31, 2021 08:13
1bddef2
to
0e75bbe
Compare
RebeccaStevens
force-pushed
the
next
branch
3 times, most recently
from
August 3, 2021 02:00
b82622f
to
0e2c490
Compare
Closing in favor of #255 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Breaking Change
This change will require a new major release.
Status: Blocked
Progress on this issue is currently not possible.
Type: Enhancement
Enhancement of the code, not introducing new features.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix #153